-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
login functions device flow proof-of-concept #498
base: main
Are you sure you want to change the base?
login functions device flow proof-of-concept #498
Conversation
Git2Gus App is installed but the |
static examples = messages.getMessages('examples'); | ||
|
||
static flags = { | ||
'instance-url': Flags.string({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
considering using flags.url as alternative to flags.string
devHub: true, | ||
}); | ||
} | ||
await authInfo.save(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Save() is also called in the handle function.
Co-authored-by: peternhale <[email protected]>
@peternhale Thanks for the feedback. For the time being, this PR only exists as a conversation starter for how we can do an interactive functions login in a containerized dev environment. There are some questions to work out before we think about merging, like:
|
What does this PR do?
This PR is a proof-of-concept that adds the
sf login functions device
command. This command uses the Salesforce device flow to log in to an org, then uses the resulting token as the subject token for the functions API token exchange.The code borrows heavily from patterns established by existing commands
sfdx auth:device:login
andsf login functions jwt
.What issues does this PR fix or reference?
W-11635097